Course Overview

The classical approach is always linked to waterfall, although Scrum came into existence in the eighties and made it visible and accepted in the form of Scrum Agile under Agile. This course provides that traditional mix wherein Agile software development with Scrum framework, known for story boards, iterative method, daily stand-ups, and prioritized items. The focused work within a self-managing team renders it highly effective and productive. You can find more information on the basics, concepts, structure, development, roles, responsibilities, sprint, lean, project management and most importantly the reasons as to why businesses embrace Agile methodology shifting gears from traditional method of working.

Reviews

Fundamental knowledge of Project Management
Experienced working on Scrum framework-based projects or familiar with Agile practice [not a prerequisite nor a requirement but 'good to have' feature]
Awareness of Agile and Scrum basics

1.Agile& Scrum Overview
2.Sprints and iterations
3.Technical Practices
4.Project Management
5.Management Practices
6.Roles
7.Lean
8.Common Problems and Resolutions

1. What is agile?
Agile is an approach that employs people-oriented organizational models, collaboration, and shared values. Tenets of agile philosophy are listed by the Agile Manifesto. Agile employs rolling wave planning; iterative and incremental delivery; quick and elastic response to change; and open communication among teams, stakeholders, and customers. Numerous agile methodologies follow these tenets, including Scrum, XP, Lean and Test-driven Development (TDD).

2. Some examples of agile principles and Practices?
Agile principles and practices are:
Early, measurable return on investment through defined, iterative delivery of product increments.
High visibility of project progress enables early identification and resolution or monitoring of problems.
Continuous involvement of the customer throughout the product development cycle.
Empowerment of the business owner to make decisions required to meet goals.
Flexibility to adapt to changing business needs, providing greater control over requirement changes.
Less waste of product and process

3.What does agile principle and practice bring to an organization?
Organizations utilizing agile principle and practice have recorded the value they obtain from these methods:
Flexible in accommodating changing business requirements, allowing the organization to exert more control over adding, modifying, or eliminating requirements.
Early and ongoing customer feedback enhances communication and enables business owners who are able to receive and scrutinize vital information required to make decisions to guide the project during the development process.
Early quantifiable return on investment.
High visibility and control of the progress of the project resulting in early signs of issues.
Incremental delivery as opposed to a one-time complete delivery at the conclusion of the project. Eliminates product and process waste.

4.What are some examples of agile principles and Practices?
• Examples of agile principles and practices are:
Early, measurable return on investment through defined, iterative delivery of product increments.
High visibility of project progress allows early identification and resolution or monitoring of problems.
Continuous involvement of the customer throughout the product development cycle.
Empowerment of the business owner to make decisions needed to meet goals.
Adaptation to changing business needs, giving more influence over requirement changes.
Less product and process waste

5.What does agile principles and practices add to a company?
Companies that apply agile principles and practices have recorded the value
that they realize from these methods:
Flexible to the changing needs of the business, providing the organization with more control over adding, modifying, or deleting requirements.
Early and ongoing customer input enhances communication and informs business owners capable of receiving and seeing important information required to make decisions to guide the project throughout the development lifecycle.
Early measurable return on investment.
High visibility and control over the project development resulting in early signs of issues.
Incremental delivery instead of a one-time final delivery at the end of the project. Minimizes product and process waste.